PreviousNextTracker indexSee it online !

(84/308) 771 - Editing Javascript causes CPU spike

I'm getting a drastic CPU spike when loading the effects.js (attatched) file from the script.aculo.us (http://script.aculo.us) library on my work machine. The CPU usage then hovers around 50% and only returns to normal after exiting JEdit.

At work I run JEdit 4.3pre8 (but this was occurring on the last stable release too) under Java 1.5.0_08 on a Windows XP box with the following plugins installed:

Ant Farm 1.5.4 Loaded
AntPlugin 1.6.5.1 Loaded
Archive 0.4.2 Loaded
Beauty 0.2.1 Loaded
BufferList 1.1 Loaded
BufferTabs 0.8.3 Loaded
Code2HTML 0.5 Loaded
Common Controls 0.9.1 Loaded
Console 4.3.0 Loaded
CssEditor 0.4 Loaded
ErrorList 1.4.2 Loaded
FTP 0.8 Loaded
Info Viewer 1.5.9 Loaded
Jakarta Commons 0.4.4 Loaded
JDiff Plugin 1.5.1 Loaded
Latest Version Check 1.5 Loaded
PHPParserPlugin 1.2.3 Loaded
Project Viewer 2.1.3.5 Loaded
QuickNotepad 4.3 Loaded
SideKick 0.6.7 Loaded
SQL 1.03 Loaded
XercesPlugin 2.8.0 Loaded
XML 2.0.4 Loaded

Submitted rev01001111 - 2006-12-14 16:39:12 Assigned daleanson
Priority 5 Labels
Status open Group None
Resolution duplicate

Comments

2006-12-14 16:39:12
rev01001111

effects.js file

effects.js (37.4Kio)

2006-12-14 16:55:28
kpouer

Logged In: YES
user_id=285591
Originator: NO

I think it is related with bug 1610416.
If you are at 50% cpu, you must have a dual core, isn't it ?

2006-12-14 16:55:28
kpouer

- **assigned_to**: nobody --> daleanson

2006-12-19 23:20:22
daleanson

Logged In: YES
user_id=187628
Originator: NO

Yes, this is the same bug as 1610416, which I haven't figured out yet.

2006-12-19 23:20:22
daleanson

- **status**: open --> closed-duplicate

2006-12-21 16:18:28
daleanson

- **status**: closed-duplicate --> open-duplicate

2006-12-21 16:18:28
daleanson

Logged In: YES
user_id=187628
Originator: NO

Reopening this one -- it is not the same as 1610416. I've got a fix for 1610416, but it doesn't fix this one.

Technically, this isn't a bug, but practically, it is. The parser will complete on the attached effects.js file... eventually. Give it a couple of hours or so. Obviously, that's not going to happen in real life, so I'll continue to work on this.